The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Verify database model
|
|
Verify that game architecture and system implementation requirements have been addressed by the proposed database architecture Completed |
Evidence:
|
Correlate data model entities and their attributes with the game artefacts and game design requirements Completed |
Evidence:
|
Verify that entity relationships defined in the data model implement game design and game-play rules Completed |
Evidence:
|
Verify estimates of amounts of data storage required and data types defined by the data model Completed |
Evidence:
|
Document design inconsistencies Completed |
Evidence:
|
Review database model and address and correct inconsistencies Completed |
Evidence:
|
Define database test data Completed |
Evidence:
|
Create physical database design
|
|
Implement conceptual data model design as a physical database design Completed |
Evidence:
|
Determine default database file size according to the data model storage estimates Completed |
Evidence:
|
Determine game data input and output workload estimates Completed |
Evidence:
|
Determine reliability and performance requirements Completed |
Evidence:
|
Define minimum hardware requirements to support input and output workload and reliability or performance requirements Completed |
Evidence:
|
Configure the database management system to use minimum hardware requirements Completed |
Evidence:
|
Refine and confirm database test data Completed |
Evidence:
|
Implement physical database prototype
|
|
Write structured query language (SQL) scripts to create physical database files according to design requirements Completed |
Evidence:
|
Write SQL scripts to create database tables Completed |
Evidence:
|
Implement primary key constraints Completed |
Evidence:
|
Implement foreign key constraints Completed |
Evidence:
|
Define and script stored procedures for selecting, inserting, updating and deleting data Completed |
Evidence:
|
Define and script Insert statements for test data Completed |
Evidence:
|
Execute SQL scripts and database, including test data Completed |
Evidence:
|
Test the database and document results
|
|
Document entity integrity tests and results Completed |
Evidence:
|
Document referential integrity tests and results Completed |
Evidence:
|
Document input and output performance tests and results Completed |
Evidence:
|
Document stored procedures tests and results Completed |
Evidence:
|
Review, evaluate and correct database performance
|
|
Review test result deficiencies Completed |
Evidence:
|
Define, evaluate and test deficiencies and ensure corrective measures are implemented Completed |
Evidence:
|
Implement corrections to database Completed |
Evidence:
|